chore(deps): bump packaging from 26.1 to 26.2#5
Merged
Conversation
Bumps [packaging](https://github.com/pypa/packaging) from 26.1 to 26.2. - [Release notes](https://github.com/pypa/packaging/releases) - [Changelog](https://github.com/pypa/packaging/blob/main/CHANGELOG.rst) - [Commits](pypa/packaging@26.1...26.2) --- updated-dependencies: - dependency-name: packaging dependency-version: '26.2' dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dgokeeffe
added a commit
that referenced
this pull request
May 16, 2026
Three dependabot PRs landed on main in the last 4 days (#1-#5) without cross-constraint checking. Two of them combined to break every deploy: 1. PR #3 bumped importlib-metadata 8.7.1 -> 9.0.0 2. PR #4 bumped opentelemetry-sdk to 1.41.1 but left opentelemetry-api at 1.41.0 (mismatched — the sdk requires the api at the same version) Symptom: `make deploy` fails at the [BUILD] step with "ERROR: Cannot install importlib-metadata==9.0.0 and mlflow-skinny==3.11.1 because these package versions have conflicting dependencies" Discovered when attempting to redeploy feat/enterprise-proxy-registry for security-fix verification. Reproduces on bare main — not specific to the feature branch. Resolution math: - mlflow-skinny 3.11.1 requires importlib_metadata>=3.7,<9 - opentelemetry-api 1.41.x requires importlib-metadata>=6.0,<8.8.0 The opentelemetry constraint is the binding one: even bumping mlflow-skinny to 3.12.0 doesn't help (it requires opentelemetry<=1.16, undoing the otel bump). The only path that keeps the otel and mlflow versions on main is reverting importlib-metadata to <8.8. Changes: - requirements.txt: importlib-metadata 9.0.0 -> 8.7.1 - requirements.txt: opentelemetry-api/proto 1.41.0 -> 1.41.1 (align with sdk) - pyproject.toml: declare `importlib-metadata<8.8` explicitly so dependabot won't try this bump again until upstream widens caps Verified with `uv pip install --dry-run -r requirements.txt` — resolves cleanly. Ready to deploy. Co-authored-by: Isaac
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps packaging from 26.1 to 26.2.
Release notes
Sourced from packaging's releases.
Changelog
Sourced from packaging's changelog.
Commits
84a87eeBump for release4a616b6docs: a few more updates to prepare for 26.2 (#1176)9de6f44ci: use native uv integration in rtd (#1175)bc76e14chore: update changelog for 26.2 (#1161)3f00091tests: add a pickle check (#1174)48a8a06fix: make Requirements/Markers pickle-safe (#1171)823b44efix: make Tags pickle-safe (#1170)4bed32dfix: make Specifier / SpecifierSet pickle-safe (#1168)963118efix: re-export ExceptionGroup for now (#1164)66e34a8docs(specifiers): add is_unsatisfiable() usage example (#1166)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)